<!DOCTYPE html>
<html>
<!-- Created by GNU Texinfo 7.1, https://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<!-- Copyright © 1988-2023 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with the
Invariant Sections being "Funding Free Software", the Front-Cover
Texts being (a) (see below), and with the Back-Cover Texts being (b)
(see below).  A copy of the license is included in the section entitled
"GNU Free Documentation License".

(a) The FSF's Front-Cover Text is:

A GNU Manual

(b) The FSF's Back-Cover Text is:

You have freedom to copy and modify this GNU Manual, like GNU
     software.  Copies published by the Free Software Foundation raise
     funds for GNU development. -->
<title>Fragments (GNU Compiler Collection (GCC) Internals)</title>

<meta name="description" content="Fragments (GNU Compiler Collection (GCC) Internals)">
<meta name="keywords" content="Fragments (GNU Compiler Collection (GCC) Internals)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta name="viewport" content="width=device-width,initial-scale=1">

<link href="index.html" rel="start" title="Top">
<link href="Option-Index.html" rel="index" title="Option Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="index.html" rel="up" title="Top">
<link href="Collect2.html" rel="next" title="Collect2">
<link href="Host-Config.html" rel="prev" title="Host Config">
<style type="text/css">
<!--
a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
span:hover a.copiable-link {visibility: visible}
-->
</style>


</head>

<body lang="en">
<div class="chapter-level-extent" id="Fragments">
<div class="nav-panel">
<p>
Next: <a href="Collect2.html" accesskey="n" rel="next"><code class="code">collect2</code></a>, Previous: <a href="Host-Config.html" accesskey="p" rel="prev">Host Configuration</a>, Up: <a href="index.html" accesskey="u" rel="up">Introduction</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Option-Index.html" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<h2 class="chapter" id="Makefile-Fragments"><span>20 Makefile Fragments<a class="copiable-link" href="#Makefile-Fragments"> &para;</a></span></h2>
<a class="index-entry-id" id="index-makefile-fragment"></a>

<p>When you configure GCC using the <samp class="file">configure</samp> script, it will
construct the file <samp class="file">Makefile</samp> from the template file
<samp class="file">Makefile.in</samp>.  When it does this, it can incorporate makefile
fragments from the <samp class="file">config</samp> directory.  These are used to set
Makefile parameters that are not amenable to being calculated by
autoconf.  The list of fragments to incorporate is set by
<samp class="file">config.gcc</samp> (and occasionally <samp class="file">config.build</samp>
and <samp class="file">config.host</samp>); See <a class="xref" href="System-Config.html">The <samp class="file">config.build</samp>; <samp class="file">config.host</samp>; and <samp class="file">config.gcc</samp> Files</a>.
</p>
<p>Fragments are named either <samp class="file">t-<var class="var">target</var></samp> or <samp class="file">x-<var class="var">host</var></samp>,
depending on whether they are relevant to configuring GCC to produce
code for a particular target, or to configuring GCC to run on a
particular host.  Here <var class="var">target</var> and <var class="var">host</var> are mnemonics
which usually have some relationship to the canonical system name, but
no formal connection.
</p>
<p>If these files do not exist, it means nothing needs to be added for a
given target or host.  Most targets need a few <samp class="file">t-<var class="var">target</var></samp>
fragments, but needing <samp class="file">x-<var class="var">host</var></samp> fragments is rare.
</p>

<ul class="mini-toc">
<li><a href="Target-Fragment.html" accesskey="1">Target Makefile Fragments</a></li>
<li><a href="Host-Fragment.html" accesskey="2">Host Makefile Fragments</a></li>
</ul>
</div>



</body>
</html>
